-
Notifications
You must be signed in to change notification settings - Fork 904
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Documentation for Monitoring #877
base: dev
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No issues flagged.
Standard Input can make mistakes. Check important info.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Looks good to me! Reviewed everything up to 7ecb62a in 11 seconds
More details
- Looked at
265
lines of code in1
files - Skipped
0
files when reviewing. - Skipped posting
3
drafted comments based on config settings.
1. docs/monitoring.md:8
- Draft comment:
Typo: 'Montoring' should be 'Monitoring'. - Reason this comment was not posted:
Confidence changes required:50%
The word 'Monitoring' is misspelled as 'Montoring'.
2. docs/monitoring.md:15
- Draft comment:
Typo in repository URL: 'juelp-ai' should be 'julep-ai'. - Reason this comment was not posted:
Confidence changes required:50%
The GitHub repository URL has a typo in the organization name 'juelp-ai', it should be 'julep-ai'.
3. docs/monitoring.md:92
- Draft comment:
Use 'docker-compose up -d' for consistency with previous command style. - Reason this comment was not posted:
Confidence changes required:50%
The command 'docker compose up -d' should be 'docker-compose up -d' for consistency with the previous command style.
Workflow ID: wflow_pCvXBgi4IU3XUvy3
You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet
mode, and more.
Thanks for the PR, @patcher9 ! I'd love to explore integrating openlit with julep even more closely. We are Apache 2.0 licensed, does that work with you guys? |
@creatorrr We love Apache 2.0! (OpenLIT is also completely Apache 2.0). And yup would love integrating with you folks! |
Hey @creatorrr I can also directly add this in the Julep code base, Such that when we detect the required ENVs, We can directly initialize monitoring for the user. What do you think? |
Hi team, I've updated the documentation to include both Julep's built-in Prometheus metrics and how to integrate with OpenLIT for better monitoring.
I am one of the maintainers of OpenLIT and we support Obserability for LLM apps built using Julep AI, It is all OpenTelemetry-native so the traces and metrics can be sent to any platform like Grafana or any OSS OTel tools
Although I know Julep has Prometheus metrics inbuilt like various countres, OpenLIT helps when the users are using LLM + VectorDBs + Other framework actions as the consolidated monitoring gives them a complete picture.
Figured the mention here might be useful for developers using Julep hence adding the reference in documentation page.
Let me know your thoughts on this and placement for this!
Important
Adds
docs/monitoring.md
with instructions for setting up monitoring using Prometheus and OpenTelemetry with OpenLIT.docs/monitoring.md
with a guide for setting up monitoring using Prometheus and Grafana.openlit
andjulep
.This description was created by for 7ecb62a. It will automatically update as commits are pushed.